Network node, ip multimedia subsystem (ims) node, over the top (ott) digital assistant, and methods in a communications network

ABSTRACT

A network node for handling access to sharing media in a media session in an Over The Top (OTT) Digital Assistant (DA). The media shall be shared between a first participant A and a second participant B in a communications network. The first participant A has access to sharing media in the media session in the OTT DA. The network node receives a request for access from the OTT DA. The request for access relates to the first participant A requesting access for the second participant B to sharing media in the media session in the OTT DA. The network node forwards the request to an IP Multimedia Subsystem (IMS) node in the communications network, to trigger the IMS node to switch on the sharing of media in the media session in the OTT DA for the second participant B, when authorised by the participant B.

TECHNICAL FIELD

Embodiments herein relate to a network node, an IP Multimedia Subsystem(IMS) node, an Over The Top (OTT) Digital Assistant (DA) and a methodstherein. In particular, they relate to handling access to sharing mediain a media session in the OTT DA.

BACKGROUND

In a typical wireless communication network, wireless devices, alsoknown as wireless communication devices, mobile stations, stations (STA)and/or user equipment (UE), communicate via a Local Area Network such asa WiFi network or a Radio Access Network (RAN) to one or more corenetworks (CN). The RAN covers a geographical area which is divided intoservice areas or cell areas, which may also be referred to as a beam ora beam group, with each service area or cell area being served by aradio network node such as a radio access node e.g., a Wi-Fi accesspoint or a radio base station (RBS), which in some networks may also bedenoted, for example, a NodeB, eNodeB (eNB), or gNB as denoted in 5thGeneration (5G). A service area or cell area is a geographical areawhere radio coverage is provided by the radio network node. The radionetwork node communicates over an air interface operating on radiofrequencies with the wireless device within range of the radio networknode. The radio network node communicates to the wireless device inDownLink (DL) and from the wireless device in UpLink (UL).

Specifications for the Evolved Packet System (EPS), also called a FourthGeneration (4G) network, have been completed within the 3rd GenerationPartnership Project (3GPP) and this work continues in the coming 3GPPreleases, for example to specify a Fifth Generation (5G) network alsoreferred to as 5G New Radio (NR). The EPS comprises the EvolvedUniversal Terrestrial Radio Access Network (E-UTRAN), also known as theLong Term Evolution (LTE) radio access network, and the Evolved PacketCore (EPC), also known as System Architecture Evolution (SAE) corenetwork. E-UTRAN/LTE is a variant of a 3GPP radio access network whereinthe radio network nodes are directly connected to the EPC core networkrather than to RNCs used in 3rd Generation (3G) networks. In general, inE-UTRAN/LTE the functions of a 3G RNC are distributed between the radionetwork nodes, e.g. eNodeBs in LTE, and the core network. As such, theRAN of an EPS has an essentially “flat” architecture comprising radionetwork nodes connected directly to one or more core networks, i.e. theyare not connected to RNCs. To compensate for that, the E-UTRANspecification defines a direct interface between the radio networknodes, this interface being denoted the X2 interface.

Multi-antenna techniques can significantly increase the data rates andreliability of a wireless communication system. The performance is inparticular improved if both the transmitter and the receiver areequipped with multiple antennas, which results in a Multiple-InputMultiple-Output (MIMO) communication channel. Such systems and/orrelated techniques are commonly referred to as MIMO.

In addition to faster peak Internet connection speeds, 5G planning aimsat higher capacity than current 4G, allowing higher number of mobilebroadband users per area unit, and allowing consumption of higher orunlimited data quantities in gigabyte per month and user. This wouldmake it feasible for a large portion of the population to streamhigh-definition media many hours per day with their mobile devices, whenout of reach of Wi-Fi hotspots. 5G research and development also aims atimproved support of machine to machine communication, also known as theInternet of things, aiming at lower cost, lower battery consumption andlower latency than 4G equipment.

Over-The-Top (OTT) services have been introduced allowing a third partytelecommunications service provider to provide services that aredelivered across an Internet Protocol (IP) network. The IP network maye.g. be a public internet or cloud services delivered via a third partyaccess network, as opposed to a carrier's own access network. OTT mayrefer to a variety of services including communications, such as e.g.voice and/or messaging, content, such as e.g. TV and/or music, andcloud-based offerings, such as e.g. computing and storage.

A further OTT service is a Digital Assistant (DA). The DA may performtasks or services upon request from a user of a UE.

IMS is a general-purpose, open industry standard for voice andmultimedia communications over packet-based IP networks. It is a corenetwork technology, that may serve as a low-level foundation fortechnologies like Voice over LTE (VoLTE) Voice over IP (VoIP),Push-To-Talk (PTT), Push-To-View, Video Calling, and Video Sharing.

The core network node may detect a keyword, which may also be referredto as a hot word, indicating that the user is providing instructions tothe DA and may forward the instructions to a network node controlled bya third party service provider, the network node may e.g. comprise a DAplatform.

An intent is an abstract description of an operation to be performed.The text describing an intent when used herein is written with the textfont Courier New Italic. An intent may be used with context#startActivity (Intent) to launch an Activity, broadcastIntent to sendit to any interested BroadcastReceiver components, andContext.startService(Intent) or Context.bindService (Intent,ServiceConnection, int) to communicate with a background Service.

An Intent provides a facility for performing late runtime bindingbetween the code in different applications. Its most significant use isin a launching of activities, where it may be thought of as the gluebetween activities. It is basically a passive data structure holding anabstract description of an action to be performed.

When a user calls startActivity( ) or startActivityForResult( ) and passit as an implicit intent, the system resolves the intent to an app thatcan handle the intent and starts its corresponding Activity. If there'smore than one app that can handle the intent, the system presents theuser with a dialog to pick which app to use.

E.g. a user is saying to its DA: “DA, call Bob”. “DA” is in this casethe keyword, or anything configured by the operator, and “Call Bob” isthe “intent” The trigger to wake up the DA is the keyword. Then theintent can be call Bob or other actions available.

The DA platform may e.g. be a bot of a company providing a certainservice, such as e.g. a taxi service or a food delivery service. AnInternet bot, also known as a web robot, a WWW robot or simply a bot, isa software application that runs automated tasks such as scripts, overthe Internet. Typically, bots perform tasks that are both simple andstructurally repetitive, at a much higher rate than would be possiblefor a human alone.

The DA platform may then forward the instructions to a further networknode, which may e.g. be an Application Server (AS) node, an agent servernode, a skill server node or similar. This further network node hasaccess to the core network node such as an IMS node via a ServiceExposure Application Programming Interface (API). Thereby the DA mayaccess the IMS node and perform services towards the core network node.

The DA platform is often required to pay a fee to the operator in orderto be reachable by the operator's DA users. The user may also berequired to pay fees to the operator and network provider for the usageof DA services. The operator may further be required to pay fees to thenetwork provider for every transaction performed via the ServiceExposure API.

A further way to implement the DA may be to provide the user with directaccess to the network node controlled by the third party serviceprovider comprising the DA platform. This may e.g. be done using adedicated UE having access to the network node. This way of implementingthe DA is commonly referred to as an OTT-controlled DA.

One of the services that can be invoked may e.g. be a telephony servicesor bot, implemented by the operator.

Some different models to support voice controlled digital assistants inIMS have been discussed. The following section shows the in-call DAfunction is implemented on each model, whereby the user avails of theirDA service to interact with and/or manipulate on-going calls. Note thatthis use case is not feasible in the OTT controlled DA but only in theOperator-controlled DA and the OTT-delegated DA.

Operator-Controlled DA

Regarding Operator-controlled DA, the operator has its own DA. All thefunctionality is contained within the operator domain such as keyworddetection, request fulfillment, media handling, service manipulationetc. Further, no service exposure towards an OTT cloud is needed.

FIG. 1 depicts an operator controlled DA. One of the services that maybe invoked is telephony services or bot, implemented by the operator.

The user Alice's UE is not impacted. The operator controls the whole DAmodel comprising keyword detection, media handling and requestfulfillment. As the operator controls the model, i.e. all session legs“in-call DA” functionality is supported in this model. A user Alice of afirst UE, a first participant, wishes to have a call, here referred toas a conference, with a second participant, the user Bob using a secondUE. The operator DA joins the conference as a participant and the logicwill only starts when the keyword is detected every time a keyword isdetected. In order to detect that the keyword has been said the operatorDA must be listening to the conference from the first moment. In otherwords, the operator is there from the start but the logic will onlystarts when the keyword is detected.

The user Alice says Alice says: “DA, call Bob”. “DA” would be thekeyword, or anything configured by the operator, for example OK, Telia,Telenor, Hey Tele2, etc. “Call Bob” is an intent. The trigger to wake upthe DA is the keyword. Then the intent may be “call Bob” or otheractions available to be used for triggering the action to call the userBob. The request may come as a hotword to wake up the DA” and “keywordsdefining the intent or request.

The keyword is sent as SIP audio data to an IMS core network node 10used by the operator. RTP is used for audio.

The IMS core network node detects the keyword comprising the RTP audiodata and invokes S04 the operator DA 10 to joins the conference.

The user Alice has an ongoing call S06 with the user Bob. The DA islistening from the start. As soon as the user says, Hi Telia, or OK,Telenor (keyword), the DA will then “wake up” and listen to the intent,i.e. call Bob.

OTT-Controlled DA

Regarding OTT-controlled DA, the keyword detection is done by the OTT DAand the request is fulfilled in the OTT cloud. Sessions are initiatedfrom the OTT DA towards the operator network. When the request relatesto service interaction and/or service manipulation, the OTT DA must useIMS service exposure APIs to access IMS capabilities. An OTT DA may e.g.comprise an OTT DA device such as a smart speaker such as e.g. Amazonecho or Google Home speakers, and e.g. the OTT DA may comprise anapplication interacting with the IMS network, and an OTT platform. AService Exposure API when used herein means an API exposing the IMScapabilities to third party applications. These capabilities are forexample call handling, message handling, supplementary service handlingetc.

FIG. 2 depicts an OTT controlled DA. Alice owns the UE and the OTT DAsuch as an Amazon echo. One of the services that may be invoked is thetelephony services or bot, implemented by the operator.

In this model, the user Alice invokes the OTT DA, such as e.g. of Amazonor Google by saying “Operator X, call Bob” “Operator X, add Charlie tothe call which is a keyword.

Keyword detection is done locally in the OTT DA. This voice keyword isstreamed to the OTT Skill Platform. Service Exposure is needed in theIMS network to access IMS capabilities from the OTT. Therefore the OTTSkill Platform sends a Hypertext Transfer Protocol(HTTP)/Representational State Transfer (REST) “add Charlie to the call”to the skill/agent server of the operator. The skill/agent server parsesthis request and matches the identity to the IMS user identity, e.g.private Id, or public Id, and sends e.g. an HTTP/REST “IMS ServiceExposure API addParticipant (Charlie) to an IMS network node.

HTTP/REST is a protocol supported between the skill server and the IMScore network. SIP/RTP in the Figures relate to the IMS protocol.

Note that this model does not support the in-call DA case as the DA hasno knowledge of ongoing sessions in the operator network.

Operator-OTT Delegated DA

Regarding Operator/OTT-delegated DA, media is handled by the operator.Keyword detection is performed by the OTT DA such as an OTT device e.g.a smart speaker, which e.g. may be a conference party. Fulfillment ofthe request done by the OTT DA application.

FIG. 3 depicts an Operator-OTT delegated DA. This model, the user suchas Alice may, in the middle of a call, referred to as conference, invokeher favorite OTT DA, e.g. of Google, or Amazon, using its keyword. Alicesays: “DA, I want to know what the capital of Spain is” wherein, “DA” isthe keyword and “I want to know what the capital of Spain” is theintent”. Only the voice from the user Alice is going up to the OTT DA,referred to as the OTT DA platform. To support this, the OTT DA must bein the call when the user Alice makes her request, the OTT DA becomes aconference participant. The OTT DA detects keyword and fulfills therequest in the same call. Fulfills the request means that the OTT DAanalyzes the user intent and will proceed with the logic to fulfill it.In the example below it will consult some sources and it will answer“The capital of Spain is Madrid”. When the user Alice's request isrelated to the IMS network, the OTT DA must use the Service ExposureAPIs to access the IMS capabilities in the IMS network. This isperformed by the OTT DA sending to the Skill/Server agent, a HTTP/REST“Keyword detect and request fulfillment”. The Skill/Server agent thensends an HTTP/REST “IMS exposed APIs” IMS node. The IMS node then willuse the IMS exposed API-s needed to fullfill the user's request. E.g.make a call to a person, or the keyword detect information is notincluded in the HTTPREST. The keyword detect is a trigger for the skillserver to start certain logic, but the info about the keyword is nevertransmitted anywhere else.

SUMMARY

As a part of developing embodiments herein the inventors identified aproblem which first will be discussed.

In the Operator-OTT delegated DA model, described above, the media ofboth call participants is reaching the served user's Digital Assistantby default.

However, participants in the call with the served user don't necessarilyconsent to their media being sent to the OTT DA. I.e., if Alice callsBob and she has Google as an OTT DA Bob does not want his audio to beuploaded to the OTT DA e.g. in the Google cloud or Amazon cloud or antOTT cloud, without his consent.

On the other hand, if the media of the participants is not sent to theOTT DA, it is limiting the number of use cases that are possible toimplement. For example, recording a call by the OTT DA, or the OTT DAbeing shared among all the participants.

Thus, if a participant's media is uploaded to the OTT DA it causes aprivacy problem, and if a participants media is not uploaded to the OTTDA it limits the number of use cases that can be implemented.

An object of embodiments herein is improve the performance of acommunications network using OTT DAs.

According to an aspect of embodiments herein, the object is achieved bya method performed by a network node, for handling access to sharingmedia in a media session in an Over The Top, OTT Digital Assistant, DA.The media shall be shared between a first participant A and a secondparticipant B in a communications network. The first participant A hasaccess to sharing media in the media session in the OTT DA. The networknode receives a request for access from the OTT DA. The request foraccess relates to the first participant A requesting access for thesecond participant B to sharing media in the media session in the OTTDA. The network node forwards the request to an IP Multimedia Subsystem,IMS, node in the communications network, to trigger the IMS node toswitch on the sharing of media in the media session in the OTT DA forthe second participant B, when authorised by the participant B.

According to another aspect of embodiments herein, the object isachieved by a method performed by an IP Multimedia Subsystem, IMS, node,for handling access to sharing media in a media session in an Over TheTop, OTT Digital Assistant, DA. The media shall be shared between afirst participant A and a second participant B in a communicationsnetwork. The first participant A has access to sharing media in themedia session in the OTT DA. The IMS node receives a request for accessfrom a network node. The request relates to the first participant Arequesting access for the second participant B to sharing media of themedia session in the OTT DA. The request is received via the OTT DA. TheIMS node sends a request to the second participant B to authorise thesharing of the media of the media session in the OTT DA for the secondparticipant B. The IMS node is then triggered to switch on the sharingof media of the media session in the OTT DA for the second participantB, when authorised by the participant B.

According to a further aspect of embodiments herein, the object isachieved by a method performed by an Over The Top, OTT DigitalAssistant, DA, for handling access to sharing media in a media sessionin the OTT DA. The media shall be shared between a first participant Aand a second participant B in a communications network. The firstparticipant A has access to sharing media in the media session in theOTT DA.

The OTT DA receives a request for access from the first participant A.The request relates to the first participant A requesting access for thesecond participant B to sharing media of the media session in the OTTDA. The request is received as a intent chosen by the first participantA to activate a request for access.

Triggered by the intent, the OTT DA sends the request via a network nodeserver to an IP Multimedia Subsystem, IMS, node in the communicationsnetwork, to trigger the IMS node 130 to switch on the sharing of mediain the media session in the OTT DA 125 for the second participant B whenauthorised by the second participant B.

According to a yet further aspect of embodiments herein, the object isachieved by a network node configured to handle access to sharing mediain a media session in an Over The Top, OTT Digital Assistant, DA. Themedia shall be shared between a first participant A and a secondparticipant B in a communications network. The first participant A isadapted to have access to sharing media in the media session in the OTTDA. The network node is further configured to:

Receive from the OTT DA, a request for access, which request is adaptedto relate to the first participant A requesting access for the secondparticipant B to share media of the media session in the OTT DA, and

forward the request to an IP Multimedia Subsystem, IMS, node in thecommunications network, to trigger the IMS node to switch on the sharingof media of the media session in the OTT DA for the second participant Bwhen authorised by the participant B.

According to an aspect of embodiments herein, the object is achieved byan IMS node configured to handle access to sharing media of a mediasession in an Over The Top, OTT Digital Assistant, DA. The media is tobe shared between a first participant A and a second participant B in acommunications network. The first participant A has access to sharingmedia in the media session in the OTT DA. The IMS node is furtherconfigured to:

Receive a request for access from a network node, which request relatesto the first participant A requesting access for the second participantB to sharing media of the media session in the OTT DA, which request isadapted to be received via the OTT DA, send a request to the secondparticipant B to authorise the sharing of the media of the media sessionin the OTT DA for the second participant B, and trigger to switch on thesharing of media of the media session in the OTT DA for the secondparticipant B, when authorised by the participant B.

According to another aspect of embodiments herein, the object isachieved by an Over The Top, OTT Digital Assistant, DA, configured tohandling access to sharing media in a media session in the OTT DA. Themedia is adapted to be shared between a first participant A and a secondparticipant B in a communications network. The first participant A isadapted to have access to share media in the media session in the OTTDA. The OTT DA is further configured to:

Receive a request for access from the first participant A, which requestfor access is adapted to relate to the first participant A requestingaccess for the second participant B to share media of the media sessionin the OTT DA, and which request is adapted to be received as a intentchosen by the first participant A to activate a request for access, and

triggered by the intent, send the request for access via a network nodeagent server to an IP Multimedia Subsystem, IMS, node in thecommunications network 100, to trigger the IMS node to switch on thesharing of media in the media session in the OTT DA for the secondparticipant B, when authorised by the second participant B.

An advantage of embodiments herein is that this mechanism allows the OTTDA to get not just the media coming from its served first user but fromall the call participants such as the second user, after they consent toit. The OTT DA may then implement use cases such as recording andstoring a call in the OTT DA or sharing the OTT DA such as a DA amongall call participants.

Another advantage of embodiments herein is the respect of regulationsand privacy of user's. Further, it is possible to share a DigitalAssistant among the call participants and to implement services likeCall Translation and Call Recording.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of embodiments herein are described in more detail withreference to attached drawings in which:

FIG. 1 is a schematic block diagram illustrating prior art.

FIG. 2 is a schematic block diagram illustrating prior art.

FIG. 3 is a schematic block diagram illustrating prior art.

FIG. 4 is a schematic block diagram illustrating embodiments of acommunications network.

FIG. 5 is a sequence diagram depicting an embodiments of a method in acommunications network.

FIG. 6 is a flowchart depicting embodiments of a method in a OTT DA.

FIG. 7 is a flowchart depicting embodiments of a method in a networknode.

FIG. 8 is a flowchart depicting embodiments of a method in an IMS node.

FIG. 9 is a schematic overview depicting embodiments of a communicationsnetwork.

FIGS. 10a and b are schematic block diagrams illustrating embodiments ofa network node.

FIGS. 11a and b are schematic block diagrams illustrating embodiments ofan IMS node.

FIGS. 12a and b are schematic block diagrams illustrating embodiments ofan OTT DA.

FIG. 13 schematically illustrates a telecommunication network connectedvia an intermediate network to a host computer.

FIG. 14 is a generalized block diagram of a host computer communicatingvia a base station with a user equipment over a partially wirelessconnection.

FIGS. 15 to 18 are flowcharts illustrating methods implemented in acommunication system including a host computer, a base station and auser equipment.

DETAILED DESCRIPTION

Example embodiments herein provide an API exposed by an IMS networknode, referred to as IMS node, so that a DA platform, also referred toas DA OTT, OTT client and OTT DA, can request access to media related tothe participants in a conference call, only when their consent isgranted.

Since the users participating in the call may not have a contractualrelationship with the OTT DA related to the DA platform, an informationmessage will be be sent to the participant. This message may e.g. be anaudio or text message. Depending on the regulations, if explicit consentis required, the IMS node must request for the participants, i.e. user'sinput and get the consent.

The network media control function may ensure that the media of allconsensual participants will then be uploaded to the OTT DA. The consentmay apply only for the duration of the session.

Embodiments herein may standardize an API to:

-   -   Trigger the request to the IMS node in the IMS network to switch        on/off the media towards the OTT DA.    -   Send an information message to all participants in the call with        the consent request.    -   If explicit consent is needed, send a consent request and        collect the answer from all participants. Only the media of        those consenting will be included in the media leg toward the        OTT DA.

New API may be provided:

accessMediaParticipants (participant list, on off, info message)

Parameters:

-   -   participant list, a list of participants the OTT DA wants to        access the media.    -   info message, a message informing the participants user about        whether the DA is accessing their media.    -   on/off, indicates whether the access to the media should be        toggled on or off.

Returns: consentanswer_list is an answer from participants giving theirconsent. It should be noted that the participant identities may beobfuscated.

This mechanism allows the OTT DA to get not just the media coming fromits served user but from all the call participants, after they consentto it. The OTT DA may then implement use cases such as e.g. recordingand storing a call in the OTT platform or sharing the OTT DA among allcall participants.

FIG. 4 is a schematic overview depicting a communications network 100wherein embodiments herein may be implemented. The communicationsnetwork 100 may be a wireless communications network and comprises oneor more RANs 104 and one or more CNs 106. The wireless communicationsnetwork 100 may use 5G NR but may further use a number of otherdifferent technologies, such as, (LTE), LTE-Advanced, Wideband CodeDivision Multiple Access (WCDMA), Global System for Mobilecommunications/enhanced Data rate for GSM Evolution (GSM/EDGE),Worldwide Interoperability for Microwave Access (WiMax), or Ultra MobileBroadband (UMB), just to mention a few possible implementations.

Network nodes operate in the wireless communications network 100, suchas one or more radio network nodes 110 providing radio coverage to UEsin the

Each radio network node 110 provides radio coverage over a geographicalarea by means of antenna beams. The geographical area may be referred toas a cell, a service area, beam or a group of beams. The radio networknode 110 may be a transmission and reception point e.g. a radio accessnetwork node such as a base station, e.g. a radio base station such as aNodeB, an evolved Node B (eNB, eNode B), an NR Node B (gNB), a basetransceiver station, a radio remote unit, an Access Point Base Station,a base station router, a transmission arrangement of a radio basestation, a stand-alone access point, a Wireless Local Area Network(WLAN) access point, an Access Point Station (AP STA), an accesscontroller, a UE acting as an access point or a peer in a Device toDevice (D2D) communication, or any other network unit capable ofcommunicating with a UE within the cell served by the radio network node110 depending e.g. on the radio access technology and terminology used.

UEs such as a first UE A and a second UE B operate in the communicationnetwork 100. The UEs A and B may e.g. be a mobile station, a non-accesspoint (non-AP) STA, a STA, a user equipment and/or a wireless terminals,an NB-IoT device, an eMTC device and a CAT-M device, a WiFi device, anLTE device and an NR device communicate via one or more Access Networks(AN), e.g. RAN, to one or more core networks (CN). It should beunderstood by the skilled in the art that “UE” is a non-limiting termwhich means any terminal, wireless communication terminal, wirelessdevice, Device to Device (D2D) terminal, or node e.g. smart phone,laptop, mobile phone, sensor, relay, mobile tablets, television units oreven a small base station communicating within a cell. According toexample embodiments herein, the UEs A and B are connected in call,referred to as a conference wherein first UE A is a first participant Ain the call and wherein the second UE B is a second participant B in thecall.

An OTT DA 125 operates in the communications network 100. The OTT DA 125may e.g. be a DA comprised in a an OTT DA platform also referred to as aOTT platform 151, e.g. in a cloud 101. When used herein, the OTT DA 125and the OTT platform 151 may be seen as one unit, i.e. that the OTT DA125 is associated with or comprises the OTT platform 151. An OTT clientis the entity that sends the requests towards the skills server.

The CN further comprises a core network node such as the IMS node 130comprised in an IMS network. the IMS node 130 is used for servingrequests coming via a Service Exposure API.

The IMS node 130 may be connected to a network node 150. The networknode 150 may be located in the cloud 101 as depicted in FIG. 1, in theCN or in a third Party domain of the communications network. The networknode 150 may be a server such as a skill server or an agent server.

Furthermore, the OTT DA 125 and the network node 150 may be collocatednodes, stand-alone nodes or distributed nodes comprised in the cloud101.

The method will first be described from a helicopter perspective as asignalling diagram showing the involved nodes such as the OTT DA 125,the network node 110, and the IMS node 130 with reference to FIG. 5.Thereafter embodiments of the method as seen from the perspective ofeach respective net the OTT DA 125, the network node 110, and the IMSnode 130 will be individually described one by one with reference torespective flow charts of FIGS. 6, 7 and 8.

An example scenario of embodiments herein before starting the method maybe:

Alice is a OTT DA 125 user, she owns the OTT DA 125 which is in thisexample a DA. Alice is in a conference call with another user Bob. Aliceis a first participant A in the conference call and Bob is a secondparticipant B in the conference call. Alice has already access to theOTT DA 125, e.g. since she owns it. The OTT DA 125 may be seen as aparticipant in the conference call. However, Bob has not access to theOTT DA 125 yet, so his media is not shared at the OTT DA 125. Theconference call may be referred to as call or media call.

Alice wants to share media in the OTT DA 125 from other participants inthe conference call, such as the second participant B.

Example embodiments of a method performed in the communications network100 for handling access to sharing media in a media session in the OTTDA 125, will now be described with reference to a sequence diagramdepicted in FIG. 5. In this example the first participant A is referredto as Alice, and the second participant B a is referred to as Bob.

Action 501. Alice sets up a call such as a media session with Bob.Initial media of the media session flows from the IMS Core Network, suchas the IMS node 130, to and from Alice and Bob. At this point also themedia from Alice is going towards OTT DA 125.

Action 502. Media from the OTT DA 125 is sent to both Alice and Bob, butno media from Bob is sent in the OTT DA 125 respecting Bob's privacy. Inthis example, the first participant Alice is associated to e.g. owns theOTT DA 125. Therefore, only media such as the voice from Alice is, insome embodiments automatically, uploaded to the OTT DA 125, in thisexample represented by a OTT.

Action 503. Alice says one or more intents to the OTT DA 125, such ase.g.: DA, request access for the participant Bob, or DA, request accessfor all participants, if more participants than Bob.

Action 504. The OTT DA 125 detects the one or more keywords said byAlice. The keywords will trigger the OTT DA 125, e.g. its associated OTTDA platform 151. The OTT DA 125 may just detect the keyword, later on itis up to the OTT DA platform 151 to process the intents and send to theconfigured network node 150 such as the skill server, to act accordingto some predetermined rules. In this example this starts the process ofrequest an accept from Bob if Bob accepts to share his media on the OTTDA 125. The accept is also referred to as authorization and consensus.

Action 505. Thus, upon detecting the one or more keywords, the OTT DA125 sends via the OTT DA platform 151 to the network node 150 to processthe intents and to send a request for access, which in this example isan agent server. The request for access relates to the first participantAlice requesting access for the second participant Bob to share media inthe media session in the OTT DA 125.

Action 506. Based on the one or more keywords, the network node 150 mayretrieve e.g. create information e.g. a list of participants comprisingat least the second participant Bob, that the first participant Alicewishes to share the media with in the OTT DA 125. This means that theOTT DA 125 detects the keyword if it is wanted that the secondparticipant Bob to be able to use it, or the OTT platform 151 of the OTTDA 125 if it is wanted to do services as recording.

The network node 150 has access to the IMS node 130 and therefore sendsthe request for access IMS node 130, requesting access for Bob to sharemedia of the media session in the OTT DA 125. The request for access maycomprise the list of participants that the first participant Alicewishes to share the media with in the OTT DA 125.

Action 507. The IMS node 130 receives the request for access from thenetwork node 150, e.g. comprising the list of participants that thefirst participant Alice wishes to share the media with in the OTT DA125. Upon receiving the request for access list of participantscomprising at least the second participant Bob, the IMS node 130 sends arequest to the second participant Bob to authorise the sharing of themedia of the media session in the OTT DA 125 for the second participantBob.

Action 508. Bob receives the request and responds in Action 509, to theIMS node 130, whether or not the sharing of the media of the mediasession in the OTT DA 125 for Bob is authorised.

Action 509 The IMS node 130 receives the response from Bob, and onlytriggers to switch on the sharing of media of the media session in theOTT DA 125 for the second participant Bob if authorized by Bob in theresponse.

Action 510. So, if authorized by Bob also media from Bob is sent to theOTT DA 125.

The media is shared between a first participant A and a secondparticipant B in a communications network 100, which first participant Ahas access to sharing B's media in the media session with the OTT DA125, wherein the OTT DA 125 may be a participant on the media session.

Method in the OTT DA 125

Example embodiments of a method performed by a method performed by theOTT DA 125 for handling an access to share media in a media session inthe OTT DA 125, will now be described with reference to a flowchartdepicted in FIG. 6.

The media shall be shared between the first participant A and the secondparticipant B in the communications network 100. The first participant Ahas access to sharing media in the media session in the OTT DA 125. TheOTT DA 125 e.g. is a participant on the media session Further, in someembodiments, the network node 150 is collocated with the OTT DA 125.

As mentioned above, the first participant A has access to sharing mediain the media session in the OTT DA 125. This means that initially, onlythe first participant A e.g.

Alice's media is being sent towards the OTT DA 125 also referred to asthe digital assistant, meanwhile the second participant B e.g. Bob canlisten and/or see the media coming from both Alice and the OTT DA 125.

Action 601

The OTT DA 125 receives a request for access from the first participantA. The request relates to the first participant A requesting access forthe second participant B to sharing media of the media session in theOTT DA 125. The request is received as a intent chosen by the firstparticipant A to activate a request for access. The request is receivedas an intent. Keyword is used to wake up the logic, intent is the logicrequested. As mentioned above the request comes as a hotword to wake upthe DA” and “keywords defining the intent or request.

E.g. the first participant Alice says one or more intents to the OTT DA125, such as e.g.: DA, request access for the second participant Bob,

Action 602

Triggered by the intent, the OTT DA 125 sends the request via a networknode 150, such as an agent server, to the IMS node 130 in thecommunications network 100. May be referred to as triggered by thekeyword, the OTT DA 125 sends the request corresponding to the intent.This is to trigger the IMS node 130 to switch on the sharing of media inthe media session in the OTT DA 125 for the second participant B whenauthorised by the second participant B.

Method in the Network Node 150

Example embodiments of a method performed by a method performed by thenetwork node 150 for handling an access to share media in a mediasession in the OTT DA 125, will now be described with reference to aflowchart depicted in FIG. 7. The media shall be shared between thefirst participant A and the second participant B in the communicationsnetwork 100. The first participant A has access to sharing media in themedia session in the OTT DA 125. The OTT DA 125 e.g. is a participant onthe media session The network node 150 may e.g. be represented by anyone out of: an agent server, a skill server, an actions server, acapsules server. Further, in some embodiments, the network node 150 iscollocated with the OTT DA 125.

The method comprises the following actions, which actions may be takenin any suitable order.

Action 701

E.g. the first participant A, who already has access to share media inthe media session in the OTT DA 125, asks for participants such as allother participants in the conference call including the secondparticipant B, to have access to share media in the media session in theOTT DA 125. This is performed to start the process of receivingconsensus also referred to as acknowledge, from the other participantsbefore accessing the other participants to share media in the mediasession in the OTT DA 125. Thus, the network node 150 receives a requestfor access from the OTT DA 125. The request for access relates to thefirst participant A requesting access for the second participant B tosharing media in the media session in the OTT DA 125. The request issent to the network node 150, such as e.g. the skill or agent server,since it acts like a gateway into the IMS network and knows to which IMSnode the request shall be sent. The IMS node 130 exposes IMScapabilities via some API-s. The OTT cloud cannot really speak the IMS“language” so the network node such as the skill server is needed toanalyse the request coming from the OTT cloud and translate it to theIMS API-s.

Action 702

As mentioned above, the network node 150, such as e.g. the skill oragent server, knows where to send the request and therefore forwards therequest to the correct IMS node, here the IMS node 130. The network node150 forwards the request to the IMS node 130 in the communicationsnetwork 100. This is to trigger the IMS node 130 to switch on thesharing of media in the media session in the OTT DA 125 for the secondparticipant B, when authorised by the participant B. The IMS node 130will take care of the obtaining of the authorizations from theconcerning participants, by sending requests to each respectiveconcerning participant. The IMS node 130 will trigger to switch on thesharing of media in the media session in the OTT DA 125 for eachrespective participant, including the second participant B, only whenauthorised by the respective participant.

Method in the IMS Node 130

Example embodiments of a method performed by a method performed by theIMS node 130 for handling an access to share media in a media session inthe OTT DA 125, will now be described with reference to a flowchartdepicted in FIG. 8. The media shall be shared between the firstparticipant A and the second participant B in the communications network100. The first participant A has access to sharing media in the mediasession in the OTT DA 125. The OTT DA 125 e.g. is a participant on themedia session

The method comprises the following actions, which actions may be takenin any suitable order.

Action 801

In some embodiments, the IMS node 130 exposes an Application ProgramInterface (API) to the network node 150. It may only be the network node150 that knows how to talk to the IMS node and can translate from theOTT platform or OTT DA 125 “language” to the IMS “language”. Everydifferent OTT DA have a different interface, so it is up to the networknode 150 to translate to the one that IMS is offering. The wording toexpose the API when used herein, means to enable some actions to beaccessed through some means. The API comprises parameters for making therequest for access a participants, comprising the second participant B,to share media of a media session in the OTT DA 125. And further, toreceive from participants, comprising the second participant B, anauthorisation for sharing of the media in the OTT DA 125 in return to arequest. API parameters when used herein means the needed input for therequested actions to be executed.

The API parameters may relate to any one out of:

-   -   A list of participants, comprising the second participant B,        that the OTT DA 125 wants to access the media,    -   a message informing the participants, comprising the second        participant (B), about whether the OTT DA 125 is accessing their        media, and    -   an indication whether the access to the media should be switched        on or off.

Action 802

The IMS node 130 receives a request for access from the network node150. The request relates to the first participant A requesting accessfor the second participant B to sharing media of the media session inthe OTT DA 125.

Action 803

The IMS node 130 sends a request to the second participant B toauthorise the sharing of the media of the media session in the OTT DA125 for the second participant B.

Action 804

The IMS node 130 is then triggered to switch on the sharing of media ofthe media session in the OTT DA 125 for the second participant B, whenauthorised by the participant B.

Embodiments herein such as mentioned above will now be further describedand exemplified with the following example. The text below is applicableto and may be combined with any suitable embodiment described above.

Initial Media Flows from the IMS Node 130

In this example scenario, depicted in FIG. 9, Alice is the OTT DA 125user, she owns the OTT DA 125 which is in this example a DA. Alice is ina conference call with another user Bob. Alice is a first participant Ain the conference call and Bob is a second participant B in theconference call. Alice has already access to the OTT DA 125, e.g. sinceshe owns it. The OTT DA 125 may be seen as a participant in theconference call. However, Bob has not access to the OTT DA 125 yet, sohis media is not shared at the OTT DA 125. The conference call may bereferred to as call or media call.

Alice wants to share media in the OTT DA 125 from other participants inthe conference call, such as the second participant B.

It should be noted that the wordings Alice and first participant A maybe used interchangeable. Further, the wordings Bob and secondparticipant B may be used interchangeable. The wordings OTT platform,and OTT DA 125 and Digital Assistant (DA) may be used interchangeable.

This means that initially, only the first participant A e.g. Alice'smedia is being sent towards the OTT DA 125 also referred to as thedigital assistant, meanwhile the second participant B e.g. Bob canlisten and/or see the media coming from both Alice and the OTT DA 125.

This means that initially default status when setting up a call with Bobis that no media from Bob is sent to the OTT DA 125 respecting Bob'sprivacy. Therefore: The OTT platform 151 of the OTT DA 125 cannotperform any service involving Bob's media, like serving request from Bobor do any king of processing of Bob's media.

-   -   Real-Time Transport Protocol (RTP) data is only sent/received by        the IMS node 130 to and from the OTT DA 125 for Alice.    -   RTP data is sent/received by the IMS node 130 both to and from        Alice for the OTT DA 125 and Bob for Alice.    -   RTP data is sent/received by the IMS node 130 both to and from        Bob for the OTT DA 125 and Bob, for Bob.

In other words, initial media flows from the IMS node 130 according tothe following: Only the voice from Alice is going to the OTT DA 125,media from OTT DA 125 is sent to both Alice and Bob. Media from Bob issent to Alice.

Request Access for Media Call or Call Participants

According to the example, the API exposed to the network node 150 by theIMS node 130 comprises Request consent and access (on/off) to the media.This e.g. means that if it is “on” the IMS node 130 will request theconsent from Bob and in affirmative case the IMS node 130 will forwardBobs media to the OTT DA 125. If it is “off” then the IMS node 130 willstop forwarding Bob's media to the OTT DA 125.

Access for media of call participant(s) is requested, e.g. Alice saysthe intents “DA, request access for all participants' media”. Thekeyword detection is done in-call by the OTT DA 125, which is one of thecall participants. Thus the OTT DA 125 detects the keywords and requestaccess to the network node 150 which e.g. may be a Skill server or anagent server, by using IMS node exposed APIs: HTTP/REST HotWordDetectrequest Fulfillment.

The network node 150 has access to the IMS node 130 via API. Thereby theOTT platform 151 of the OTT DA 125 may via the network node 150, accessthe IMS node 130 and perform services e.g. towards a node inside the IMSnetwork, this may be any Application Server where the service exposureAPIs are available. This may be implemented in the Multimedia Telephonyservice (MMTel) Application Server (AS) for instance or develop onespecific just for this. Service Exposure is needed. This means that theApplication Server inside the IMS will serve the requests got using theexposed APIs. Thus the network node 150 forwards the request to the IMSnode 130 using IMS node exposed APIs: HTTP/REST, which is an example ofwhat kind of interface or “language” the API is using,AccessMediaParticipant.

The IMS node 130 sends and audio or a text message to the callparticipant such as to Bob, asking or informing about the media accessrequest, also referred to as requesting authorisation from the secondparticipant B.

IMS exposed APIs may comprise AUDIO or TEXT informing or asking formedia access.

Depending on the legal regulations, it may happen that the callparticipants need to give explicit permission or only need to beinformed about the media access request. Once the request has beengranted by the IMS node 130, the media flows will end up with RTP dataflow is sent/received by the IMS node 130 to and from the OTT DA 125 forboth Alice and Bob.

This means that the OTT DA 125 has now access to some participants',e.g. the second participant Bob's or all participants' media dependingif the access has been granted or not, i.e. if authorized by them. Thewordings media and data may be used interchangeable.

It should be noted that this example embodiment may be generalized forthe case where there are many participants in the call like in aconference call.

Thus, embodiments herein provide exposure from the IMS network such asthe IMS node 130 to share the user's OTT DA 125 with the callparticipants after gathering their consent.

To perform the method actions above, the network node 150 is configuredto handle an access to sharing media in a media session in the OTT DA125, and the network node 150 may comprise the arrangement depicted inFIG. 10a and FIG. 10b . The media shall be shared between the firstparticipant A and a second participant B in the communications network100. The first participant A is adapted to have access to sharing mediain the media session in the OTT DA 125. The OTT DA 125 may be adapted tobe a participant on the media session.

The network node 150 may comprise an input and output interface 1000depicted in FIG. 10a , configured to communicate e.g. with the IMS node130 and the OTT DA 125. The input and output interface 1000 may comprisea receiver (not shown) and a transmitter (not shown).

The network node 150 is configured to, e.g. by means of a receiving unit1010 in the network node 110 depicted in FIG. 10b , receive from the OTTDA 125, a request for access. The request is adapted to relate to thefirst participant A requesting access for the second participant B toshare media of the media session in the OTT DA 125.

The network node 150 is further configured to, e.g. by means of aforwarding unit 1020 in the network node 110 depicted in FIG. 10b ,forward the request to an IMS node 130 in the communications network100, to trigger the IMS node 130 to switch on the sharing of media ofthe media session in the OTT DA 125 for the second participant B whenauthorised by the participant B.

The network node 150 may be adapted to be represented by a server.Different OTT's use different names for these servers. E.g. any one outof: an agent server, a skill server as used by Amazon Alexa, Actionsused by Google, Capsules used by Samsung and there are many others.

The network node 150 may be adapted to be collocated with the OTT DA125.

The embodiments herein may be implemented through a respective processoror one or more processors, such as a processor 1030 of a processingcircuitry in the network node 150 depicted in FIG. 10a , together with arespective computer program code for performing the functions andactions of the embodiments herein. The program code mentioned above mayalso be provided as a computer program product, for instance in the formof a data carrier carrying computer program code for performing theembodiments herein when being loaded into the network node 150. One suchcarrier may be in the form of a CD ROM disc. It is however feasible withother data carriers such as a memory stick. The computer program codemay furthermore be provided as pure program code on a server anddownloaded to the network node 150.

The network node 110 may further comprise a memory 1040 depicted in FIG.10a , comprising one or more memory units to store data on. The memory1040 comprises instructions executable by the processor 1030. The memory1040 is arranged to be used to store e.g. intents, instructions,configurations and applications to perform the methods herein when beingexecuted in the network node 150.

Those skilled in the art will also appreciate that the units in theradio network node 150 mentioned above may refer to a combination ofanalogue and digital circuits, and/or one or more processors configuredwith software and/or firmware, e.g. stored in the network node 150 thatwhen executed by the respective one or more processors such as theprocessors described above. One or more of these processors, as well asthe other digital hardware, may be included in a singleApplication-Specific Integrated Circuitry (ASIC), or several processorsand various digital hardware may be distributed among several separatecomponents, whether individually packaged or assembled into asystem-on-a-chip (SoC).

In some embodiments, a computer program 1050 comprises instructions,which when executed by the respective at least one processor 1030, causethe at least one processor 1030 of the network node 110 to perform theactions above.

In some embodiments, a carrier 1060 comprises the computer program 1050,wherein the carrier 1060 is one of an electronic signal, an opticalsignal, an electromagnetic signal, a magnetic signal, an electricsignal, a radio signal, a microwave signal, or a computer-readablestorage medium.

To perform the method actions above the IMS node 130 is configured tohandle access to sharing media of a media session in the device 125, andthe IMS node 130 may comprise the arrangement depicted in FIG. 11a andFIG. 11b . The media is to be shared between a first participant A and asecond participant B in the communications network 100. The firstparticipant A has access to share media in the media session in the OTTDA 125. The OTT DA 125 may be adapted to be a participant on the mediasession

The IMS node 130 may comprise an input and output interface 1100depicted in FIG. 11a , configured to communicate e.g. with the networknode 150 and the OTT DA 125. The input and output interface 1100 maycomprise a receiver (not shown) and a transmitter (not shown).

The IMS node 130 is configured to, e.g. by means of a receiving unit1110 in the IMS node 130 depicted in FIG. 11b , receive a request foraccess from the network node 150. The request relates to the firstparticipant A requesting access for the second participant B to sharingmedia of the media session in the OTT DA 125. The request is adapted tobe received via the OTT DA 125.

The IMS node 130 is further configured to, e.g. by means of a sendingunit 1120 in the IMS node 130 depicted in FIG. 11b , send a request tothe second participant B to authorise the sharing of the media of themedia session in the OTT DA 125 for the second participant B.

The IMS node 130 is configured to, e.g. by means of a triggering unit1130 in the IMS node 130 depicted in FIG. 11b , trigger to switch on thesharing of media of the media session in the OTT DA 125 for the secondparticipant B, when authorised by the participant B.

In some embodiments, the IMS node 130 is configured to, e.g. by means ofa exposing unit 1140 in the IMS node 130 depicted in FIG. 11b , exposeto the network node 150, an API comprising parameters for making therequest for access a participants comprising the second participant B,to share media of a media session in the OTT DA 125 and to receive fromparticipants comprising the second participant B, an authorisation forsharing of the media in the OTT DA 125 in return to a request.

The API parameters may be adapted to relate to any one out of: A list ofparticipants, comprising the second participant B, the OTT DA 125 wantsto access the media, a message informing the participants, comprisingthe second participant B, about whether the OTT DA 125 is accessingtheir media, and an indication whether the access to the media should beswitched on or off.

The embodiments herein may be implemented through a respective processoror one or more processors, such as a processor 1150 of a processingcircuitry in the IMS node 130 depicted in FIG. 3, together with arespective computer program code for performing the functions andactions of the embodiments herein. The program code mentioned above mayalso be provided as a computer program product, for instance in the formof a data carrier carrying computer program code for performing theembodiments herein when being loaded into the IMS node 130. One suchcarrier may be in the form of a CD ROM disc. It is however feasible withother data carriers such as a memory stick. The computer program codemay furthermore be provided as pure program code on a server anddownloaded to the IMS node 130.

The IMS node 130 may further comprise a memory 1160 comprising one ormore memory units to store data on. The memory comprises instructionsexecutable by the processor 1150. The memory 1160 is arranged to be usedto store e.g. intents, instructions, configurations and applications toperform the methods herein when being executed in the IMS node 130.

Those skilled in the art will also appreciate that the units in theradio IMS node 130 mentioned above may refer to a combination ofanalogue and digital circuits, and/or one or more processors configuredwith software and/or firmware, e.g. stored in the IMS node 130 that whenexecuted by the respective one or more processors such as the processorsdescribed above. One or more of these processors, as well as the otherdigital hardware, may be included in a single Application-SpecificIntegrated Circuitry (ASIC), or several processors and various digitalhardware may be distributed among several separate components, whetherindividually packaged or assembled into a system-on-a-chip (SoC).

In some embodiments, a computer program 1170 comprises instructions,which when executed by the respective at least one processor 1150, causethe at least one processor 1150 of the network node 110 to perform theactions above.

In some embodiments, a carrier 1180 comprises the computer program 1170,wherein the carrier 1180 is one of an electronic signal, an opticalsignal, an electromagnetic signal, a magnetic signal, an electricsignal, a radio signal, a microwave signal, or a computer-readablestorage medium.

To perform the method actions above, the OTT DA 125 is configured tohandle access to sharing media in a media session in an OTT DA 125, andthe OTT DA 125 may comprise the arrangement depicted in FIG. 12a andFIG. 12b . The media is adapted to be shared between the firstparticipant A and the second participant B in the communications network100. The first participant A is adapted to have access to share media inthe media session in the OTT DA 125. The OTT DA 125 may be adapted to bea participant in the media session.

The OTT DA 125 may comprise an input and output interface 400 depictedin FIG. 12a , configured to communicate e.g. with the network 150 andthe IMS node 130. The input and output interface 1100 may comprise areceiver (not shown) and a transmitter (not shown).

The OTT DA 125 is configured to, e.g. by means of a receiving unit 1210in the network node 110 depicted in FIG. 12b , receive a request foraccess from the first participant A. The request for access is adaptedto relate to the first participant A requesting access for the secondparticipant B to share media of the media session in the OTT DA 125. Therequest is adapted to be received as a intent chosen by the firstparticipant A to activate a request for access.

The OTT DA 125 is further configured to, e.g. by means of a sending unit1220 in the network node 110 depicted in FIG. 12b , when triggered bythe intent, send the request for access via a network node 150 agentserver to the IMS node 130 in the communications network, to trigger theIMS node 130 to switch on the sharing of media in the media session inthe OTT DA 125 for the second participant B, when authorised by thesecond participant B.

The embodiments herein may be implemented through a respective processoror one or more processors, such as a processor 1230 of a processingcircuitry in the OTT DA 125 depicted in FIG. 12a , together with arespective computer program code for performing the functions andactions of the embodiments herein. The program code mentioned above mayalso be provided as a computer program product, for instance in the formof a data carrier carrying computer program code for performing theembodiments herein when being loaded into the OTT DA 125. One suchcarrier may be in the form of a CD ROM disc. It is however feasible withother data carriers such as a memory stick. The computer program codemay furthermore be provided as pure program code on a server anddownloaded to the OTT DA 125.

The OTT DA 125 may further comprise a memory 1240 comprising one or morememory units to store data on. The memory comprises instructionsexecutable by the processor 1230. The memory 1240 is arranged to be usedto store e.g. e.g. intents, instructions, configurations andapplications to perform the methods herein when being executed in theOTT DA 125.

Those skilled in the art will also appreciate that the units in the OTTDA 125 mentioned above may refer to a combination of analogue anddigital circuits, and/or one or more processors configured with softwareand/or firmware, e.g. stored in the OTT DA 125 that when executed by therespective one or more processors such as the processors describedabove. One or more of these processors, as well as the other digitalhardware, may be included in a single Application-Specific IntegratedCircuitry (ASIC), or several processors and various digital hardware maybe distributed among several separate components, whether individuallypackaged or assembled into a system-on-a-chip (SoC).

In some embodiments, a computer program 1250 comprises instructions,which when executed by the respective at least one processor 1230, causethe at least one processor 1230 of the OTT DA 125 10 to perform theactions above.

In some embodiments, a carrier 1260 comprises the computer program 1250,wherein the carrier 1260 is one of an electronic signal, an opticalsignal, an electromagnetic signal, a magnetic signal, an electricsignal, a radio signal, a microwave signal, or a computer-readablestorage medium.

FURTHER EXTENSIONS AND VARIATIONS

With reference to FIG. 13, in accordance with an embodiment, acommunication system includes a telecommunication network 3210 such asthe wireless communications network 100, e.g. a NR network, such as a3GPP-type cellular network, which comprises an access network 3211, suchas a radio access network, and a core network 3214. The access network3211 comprises a plurality of base stations 3212 a, 3212 b, 3212 c, suchas the network node 110, access nodes, AP STAs NBs, eNBs, gNBs or othertypes of wireless access points, each defining a corresponding coveragearea 3213 a, 3213 b, 3213 c. Each base station 3212 a, 3212 b, 3212 c isconnectable to the core network 3214 over a wired or wireless connection3215. A first user equipment (UE) e.g. the UE A such as a Non-AP STA3291 located in coverage area 3213 c is configured to wirelessly connectto, or be paged by, the corresponding base station 3212 c. A second UE3292 e.g. the first or second radio node 110, 120 or such as a Non-APSTA in coverage area 3213 a is wirelessly connectable to thecorresponding base station 3212 a. While a plurality of UEs 3291, 3292are illustrated in this example, the disclosed embodiments are equallyapplicable to a situation where a sole UE is in the coverage area orwhere a sole UE is connecting to the corresponding base station 3212.

The telecommunication network 3210 is itself connected to a hostcomputer 3230, which may be embodied in the hardware and/or software ofa standalone server, a cloud-implemented server, a distributed server oras processing resources in a server farm. The host computer 3230 may beunder the ownership or control of a service provider, or may be operatedby the service provider or on behalf of the service provider. Theconnections 3221, 3222 between the telecommunication network 3210 andthe host computer 3230 may extend directly from the core network 3214 tothe host computer 3230 or may go via an optional intermediate network3220. The intermediate network 3220 may be one of, or a combination ofmore than one of, a public, private or hosted network; the intermediatenetwork 3220, if any, may be a backbone network or the Internet; inparticular, the intermediate network 3220 may comprise two or moresub-networks (not shown).

The communication system of FIG. 13 as a whole enables connectivitybetween one of the connected UEs 3291, 3292 and the host computer 3230.The connectivity may be described as an over-the-top (OTT) connection3250. The host computer 3230 and the connected UEs 3291, 3292 areconfigured to communicate data and/or signaling via the OTT connection3250, using the access network 3211, the core network 3214, anyintermediate network 3220 and possible further infrastructure (notshown) as intermediaries. The OTT connection 3250 may be transparent inthe sense that the participating communication devices through which theOTT connection 3250 passes are unaware of routing of uplink and downlinkcommunications. For example, a base station 3212 may not or need not beinformed about the past routing of an incoming downlink communicationwith data originating from a host computer 3230 to be forwarded (e.g.,handed over) to a connected UE 3291. Similarly, the base station 3212need not be aware of the future routing of an outgoing uplinkcommunication originating from the UE 3291 towards the host computer3230.

Example implementations, in accordance with an embodiment, of the UE,base station and host computer discussed in the preceding paragraphswill now be described with reference to FIG. 14. In a communicationsystem 3300, a host computer 3310 comprises hardware 3315 including acommunication interface 3316 configured to set up and maintain a wiredor wireless connection with an interface of a different communicationdevice of the communication system 3300. The host computer 3310 furthercomprises processing circuitry 3318, which may have storage and/orprocessing capabilities. In particular, the processing circuitry 3318may comprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. The host computer3310 further comprises software 3311, which is stored in or accessibleby the host computer 3310 and executable by the processing circuitry3318. The software 3311 includes a host application 3312. The hostapplication 3312 may be operable to provide a service to a remote user,such as a UE 3330 connecting via an OTT connection 3350 terminating atthe UE 3330 and the host computer 3310. In providing the service to theremote user, the host application 3312 may provide user data which istransmitted using the OTT connection 3350.

The communication system 3300 further includes a base station 3320provided in a telecommunication system and comprising hardware 3325enabling it to communicate with the host computer 3310 and with the UE3330. The hardware 3325 may include a communication interface 3326 forsetting up and maintaining a wired or wireless connection with aninterface of a different communication device of the communicationsystem 3300, as well as a radio interface 3327 for setting up andmaintaining at least a wireless connection 3370 with a UE 3330 locatedin a coverage area (not shown in FIG. 14) served by the base station3320. The communication interface 3326 may be configured to facilitate aconnection 3360 to the host computer 3310. The connection 3360 may bedirect or it may pass through a core network (not shown in FIG. 14) ofthe telecommunication system and/or through one or more intermediatenetworks outside the telecommunication system. In the embodiment shown,the hardware 3325 of the base station 3320 further includes processingcircuitry 3328, which may comprise one or more programmable processors,application-specific integrated circuits, field programmable gate arraysor combinations of these (not shown) adapted to execute instructions.The base station 3320 further has software 3321 stored internally oraccessible via an external connection.

The communication system 3300 further includes the UE 3330 alreadyreferred to. Its hardware 3335 may include a radio interface 3337configured to set up and maintain a wireless connection 3370 with a basestation serving a coverage area in which the UE 3330 is currentlylocated. The hardware 3335 of the UE 3330 further includes processingcircuitry 3338, which may comprise one or more programmable processors,application-specific integrated circuits, field programmable gate arraysor combinations of these (not shown) adapted to execute instructions.The UE 3330 further comprises software 3331, which is stored in oraccessible by the UE 3330 and executable by the processing circuitry3338. The software 3331 includes a client application 3332. The clientapplication 3332 may be operable to provide a service to a human ornon-human user via the UE 3330, with the support of the host computer3310. In the host computer 3310, an executing host application 3312 maycommunicate with the executing client application 3332 via the OTTconnection 3350 terminating at the UE 3330 and the host computer 3310.In providing the service to the user, the client application 3332 mayreceive request data from the host application 3312 and provide userdata in response to the request data. The OTT connection 3350 maytransfer both the request data and the user data. The client application3332 may interact with the user to generate the user data that itprovides.

It is noted that the host computer 3310, base station 3320 and UE 3330illustrated in FIG. 14 may be identical to the host computer 3230, oneof the base stations 3212 a, 3212 b, 3212 c and one of the UEs 3291,3292 of FIG. 13, respectively. This is to say, the inner workings ofthese entities may be as shown in FIG. 14 and independently, thesurrounding network topology may be that of FIG. 13.

In FIG. 14, the OTT connection 3350 has been drawn abstractly toillustrate the communication between the host computer 3310 and the useequipment 3330 via the base station 3320, without explicit reference toany intermediary devices and the precise routing of messages via thesedevices. Network infrastructure may determine the routing, which it maybe configured to hide from the UE 3330 or from the service provideroperating the host computer 3310, or both. While the OTT connection 3350is active, the network infrastructure may further take decisions bywhich it dynamically changes the routing (e.g., on the basis of loadbalancing consideration or reconfiguration of the network).

The wireless connection 3370 between the UE 3330 and the base station3320 is in accordance with the teachings of the embodiments describedthroughout this disclosure. One or more of the various embodimentsimprove the performance of OTT services provided to the UE 3330 usingthe OTT connection 3350, in which the wireless connection 3370 forms thelast segment. More precisely, the teachings of these embodiments mayimprove the data rate, latency, power consumption and thereby providebenefits such as user waiting time, relaxed restriction on file size,better responsiveness, extended battery lifetime.

A measurement procedure may be provided for the purpose of monitoringdata rate, latency and other factors on which the one or moreembodiments improve. There may further be an optional networkfunctionality for reconfiguring the OTT connection 3350 between the hostcomputer 3310 and UE 3330, in response to variations in the measurementresults. The measurement procedure and/or the network functionality forreconfiguring the OTT connection 3350 may be implemented in the software3311 of the host computer 3310 or in the software 3331 of the UE 3330,or both. In embodiments, sensors (not shown) may be deployed in or inassociation with communication devices through which the OTT connection3350 passes; the sensors may participate in the measurement procedure bysupplying values of the monitored quantities exemplified above, orsupplying values of other physical quantities from which software 3311,3331 may compute or estimate the monitored quantities. The reconfiguringof the OTT connection 3350 may include message format, retransmissionsettings, preferred routing etc.; the reconfiguring need not affect thebase station 3320, and it may be unknown or imperceptible to the basestation 3320. Such procedures and functionalities may be known andpracticed in the art. In certain embodiments, measurements may involveproprietary UE signaling facilitating the host computer's 3310measurements of throughput, propagation times, latency and the like. Themeasurements may be implemented in that the software 3311, 3331 causesmessages to be transmitted, in particular empty or ‘dummy’ messages,using the OTT connection 3350 while it monitors propagation times,errors etc.

FIG. 15 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station such as anAP STA, and a UE such as a Non-AP STA which may be those described withreference to FIG. 13 and FIG. 14. For simplicity of the presentdisclosure, only drawing references to FIG. 7 will be included in thissection. In a first action 3410 of the method, the host computerprovides user data. In an optional subaction 3411 of the first action3410, the host computer provides the user data by executing a hostapplication. In a second action 3420, the host computer initiates atransmission carrying the user data to the UE. In an optional thirdaction 3430, the base station transmits to the UE the user data whichwas carried in the transmission that the host computer initiated, inaccordance with the teachings of the embodiments described throughoutthis disclosure. In an optional fourth action 3440, the UE executes aclient application associated with the host application executed by thehost computer.

FIG. 16 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station such as anAP STA, and a UE such as a Non-AP STA which may be those described withreference to FIG. 13 and FIG. 14. For simplicity of the presentdisclosure, only drawing references to FIG. 16 will be included in thissection. In a first action 3510 of the method, the host computerprovides user data. In an optional subaction (not shown) the hostcomputer provides the user data by executing a host application. In asecond action 3520, the host computer initiates a transmission carryingthe user data to the UE. The transmission may pass via the base station,in accordance with the teachings of the embodiments described throughoutthis disclosure. In an optional third action 3530, the UE receives theuser data carried in the transmission.

FIG. 17 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station such as anAP STA, and a UE such as a Non-AP STA which may be those described withreference to FIG. 13 and FIG. 14. For simplicity of the presentdisclosure, only drawing references to FIG. 17 will be included in thissection. In an optional first action 3610 of the method, the UE receivesinput data provided by the host computer. Additionally or alternatively,in an optional second action 3620, the UE provides user data. In anoptional subaction 3621 of the second action 3620, the UE provides theuser data by executing a client application. In a further optionalsubaction 3611 of the first action 3610, the UE executes a clientapplication which provides the user data in reaction to the receivedinput data provided by the host computer. In providing the user data,the executed client application may further consider user input receivedfrom the user. Regardless of the specific manner in which the user datawas provided, the UE initiates, in an optional third subaction 3630,transmission of the user data to the host computer. In a fourth action3640 of the method, the host computer receives the user data transmittedfrom the UE, in accordance with the teachings of the embodimentsdescribed throughout this disclosure.

FIG. 18 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station such as anAP STA, and a UE such as a Non-AP STA which may be those described withreference to FIG. 13 and FIG. 14. For simplicity of the presentdisclosure, only drawing references to FIG. 18 will be included in thissection. In an optional first action 3710 of the method, in accordancewith the teachings of the embodiments described throughout thisdisclosure, the base station receives user data from the UE. In anoptional second action 3720, the base station initiates transmission ofthe received user data to the host computer. In a third action 3730, thehost computer receives the user data carried in the transmissioninitiated by the base station.

When using the word “comprise” or “comprising” it shall be interpretedas non-limiting, i.e. meaning “consist at least of”.

The embodiments herein are not limited to the above described preferredembodiments. Various alternatives, modifications and equivalents may beused.

1. A method performed by a network node for handling access to sharing media in a media session in an Over The Top (OTT) Digital Assistant (DA), which media is shared between a first participant and a second participant in a communications network, in which the first participant has access to sharing media in the media session in the OTT DA, the method comprising: receiving from the OTT DA, a request for access, which request for access relates to the first participant requesting access for the second participant to sharing media in the media session in the OTT DA; and forwarding the request to an IP Multimedia Subsystem (IMS) node in the communications network, to trigger the IMS node to switch on the sharing of media in the media session in the OTT DA for the second participant, when authorised by the second participant.
 2. The method according to claim 1, wherein the network node is represented by any one out of: an agent server, a skill server, an actions server, or an capsules server.
 3. The method according to claim 1, wherein the network node is collocated with the OTT DA. 4-5. (canceled)
 6. A method performed by an IP Multimedia Subsystem (IMS) node for handling access to sharing media in a media session in an Over The Top (OTT) Digital Assistant (DA), which media is shared between a first participant and a second participant in a communications network, in which the first participant has access to sharing media in the media session in the OTT DA, the method comprising: receiving from a network node a request for access, which request relates to the first participant requesting access for the second participant to sharing media of the media session in the OTT DA; sending a request to the second participant to authorise the sharing of the media of the media session in the OTT DA for the second participant; and triggering to switch on the sharing of media of the media session in the OTT DA for the second participant, when authorised by the second participant.
 7. The method according to claim 6, further comprising: exposing to the network node an Application Program Interface (API) comprising parameters for making the request for access of participants, comprising the second participant, to share media of a media session in the OTT DA and to receive from participants, comprising the second participant, an authorisation for sharing of the media in the OTT DA in return to a request.
 8. The method according to claim 7, wherein the API parameters relate to any one out of: a list of participants, comprising the second participant, the OTT DA wants to access the media; a message informing the participants, comprising the second participant, about whether the OTT DA is accessing their media; and an indication whether the access to the media should be switched on or off. 9-10. (canceled)
 11. A method performed by an Over The Top (OTT) Digital Assistant (DA) for handling access to sharing media in a media session in the OTT DA, which media is shared between a first participant and a second participant in a communications network, in which the first participant has access to sharing media in the media session in the OTT DA, the method comprising: receiving from the first participant a request for access, which request relates to the first participant requesting access for the second participant to sharing media of the media session in the OTT DA, and which request is received as an intent chosen by the first participant to activate a request for access; and in response to being triggered by the intent, sending the request via a network node to an IP Multimedia Subsystem (IMS) node in the communications network to trigger the IMS node to switch on the sharing of media in the media session in the OTT DA for the second participant when authorised by the second participant.
 12. The method according to claim 11, wherein the OTT DA is collocated with the network node. 13-14. (canceled)
 15. A network node to handle access to sharing media in a media session in an Over The Top (OTT) Digital Assistant (DA), which media is shared between a first participant and a second participant in a communications network, in which the first participant is to have access to sharing media in the media session in the OTT DA, wherein the OTT DA is to be a participant on the media session the network node, the network node comprising: a processor; and a memory comprising instructions which, when executed by the processor, cause the network node to: receive from the OTT DA, a request for access, which request is to relate to the first participant requesting access for the second participant to share media of the media session in the OTT DA; and forward the request to an IP Multimedia Subsystem (IMS) node in the communications network, to trigger the IMS node to switch on the sharing of media of the media session in the OTT DA for the second participant when authorised by the second participant.
 16. The network node according to claim 15, wherein the network node is represented by any one out of: an agent server, a skill server, an actions server, or an capsules server.
 17. The network node according to claim 15, wherein the network node is collocated with the OTT DA.
 18. An IP Multimedia Subsystem (IMS) node to handle access to sharing media of a media session in an Over The Top (OTT) Digital Assistant (DA), which media is to be shared between a first participant and a second participant in a communications network, in which the first participant has access to sharing media in the media session in the OTT DA, wherein the OTT DA is a participant on the media session, the IMS node comprising: a processor; and a memory comprising instructions which, when executed by the processor, cause the IMS node to: receive a request for access from a network node, which request relates to the first participant requesting access for the second participant to sharing media of the media session in the OTT DA, in which request is received via the OTT DA; send a request to the second participant to authorise the sharing of the media of the media session in the OTT DA for the second participant; and trigger to switch on the sharing of media of the media session in the OTT DA for the second participant, when authorised by the second participant.
 19. The IMS node according to claim 18, wherein the IMS node is further to: expose to the network node, an Application Program Interface (API) comprising parameters for making the request for access a participants, comprising the second participant, to share media of a media session in the OTT DA and to receive from participants, comprising the second participant, an authorisation for sharing of the media in the OTT DA in return to a request.
 20. The IMS node according to claim 19, wherein the API parameters are to relate to any one out of: a list of participants, comprising the second participant, the OTT DA wants to access the media; a message informing the participants, comprising the second participant, about whether the OTT DA is accessing their media; and an indication whether the access to the media is to be switched on or off.
 21. An Over The Top (OTT) Digital Assistant (DA) for handling access to sharing media in a media session in the OTT DA, which media is to be shared between a first participant and a second participant in a communications network, in which the first participant is to have access to share media in the media session in the OTT DA, and which OTT DA is to be a participant in the media session, the OTT DA comprising: a processor; and a memory comprising instructions which, when executed by the processor cause the OTT DA to: receive a request for access from the first participant, which request for access is to relate to the first participant requesting access for the second participant to share media of the media session in the OTT DA, and in which the request is to be received as an intent chosen by the first participant to activate a request for access; and in response to being triggered by the intent, send the request for access via a network node to an IP Multimedia Subsystem (IMS) node in the communications network, to trigger the IMS node to switch on the sharing of media in the media session in the OTT DA for the second participant, when authorised by the second participant. 